Content type rationale and tagging#2730
Content type rationale and tagging#2730ltagliaferri wants to merge 7 commits intochainguard-dev:mainfrom
Conversation
Signed-off-by: ltagliaferri <[email protected]>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
SharpRake
left a comment
There was a problem hiding this comment.
A few questions/issues:
- I'd like to see a mention of this made in the Style Guide's Front matter section. Even if it's just pointing to the README.md file, I'd like to make sure this is flagged there.
- I'm not clear on when one contentType applies vs another. I think this mostly has to do with the fact that it feels like we're dealing with two different kinds of categories: conceptual, tutorial, and how-to-guide all feel distinct, but product-docs and integration feel like umbrella categories for the others. Like, most docs I'd label as integrations could be how-to-guides, and most product-docs are one of the three.
I only got about halfway through these (to content/chainguard/chainguard-images/staying-secure/updating-images/renovate/index.md [for my own reference]) but I'd like to make sure we're set on these categories and get clear the logic for when they apply before going further.
| parent: "administration" | ||
| toc: true | ||
| weight: 008 | ||
| contentType: "tutorial" |
There was a problem hiding this comment.
I'm unclear on when something is a product doc vs a tutorial (or something else). I think this is the first tutorial I've seen but I think it could go either way here.
| parent: "chainctl-usage" | ||
| weight: 025 | ||
| toc: true | ||
| contentType: "conceptual" |
There was a problem hiding this comment.
Again, unclear on when product-doc is applicable or not. It almost feels too broad to be useful.
| parent: "administration" | ||
| toc: true | ||
| weight: 010 | ||
| contentType: "how-to-guide" |
There was a problem hiding this comment.
For that matter, I'm not clear on when something is a tutorial vs. a how-to-guide.
There was a problem hiding this comment.
just double checked the README, learning-oriented vs. task-oriented makes sense but it still feels a bit fuzzy
There was a problem hiding this comment.
tutorial is more for introducing someone to something vs. how-to which is giving someone who know the general route a more detailed map
| parent: "pull-through-guides" | ||
| toc: true | ||
| weight: 005 | ||
| contentType: "product-docs" |
There was a problem hiding this comment.
IMO all the pull-through guides make more sense as how-to-guides
There was a problem hiding this comment.
I guess this is more of a question of whether you think it should sit with the product docs or not. I think I would lump integrations and product docs together for now
| contentType: "product-docs" | |
| contentType: "integration" |
| parent: "features" | ||
| weight: 007 | ||
| toc: true | ||
| contentType: "product-docs" |
There was a problem hiding this comment.
I'd call this one conceptual
| parent: "chainguard-images" | ||
| weight: 010 | ||
| toc: true | ||
| contentType: "how-to-guide" |
There was a problem hiding this comment.
I'd call this one a tutorial
SharpRake
left a comment
There was a problem hiding this comment.
Second review, some more thoughts:
- I'm a little wary of cases where all the docs in one bucket are the same contentType. For example, each Libraries doc is a product-doc, and each migration doc is a how-to
- FAQs should be conceptual, most are listed as how-tos
| parent: "chainguard-images" | ||
| weight: 015 | ||
| toc: true | ||
| contentType: "how-to-guide" |
There was a problem hiding this comment.
| contentType: "how-to-guide" | |
| contentType: "tutorial" |
content/chainguard/chainguard-images/staying-secure/working-with-scanners/false-results.md
Outdated
Show resolved
Hide resolved
| }, | ||
| ] | ||
|
|
||
| contentType: "conceptual" |
There was a problem hiding this comment.
IMO all the vuln-comparison docs should be product-docs
There was a problem hiding this comment.
I am thinking we should get rid of them but I need to check with some other stakeholders on that.
| @@ -12,6 +12,7 @@ menu: | |||
| parent: "libraries" | |||
| weight: 005 | |||
| toc: true | |||
| contentType: "product-docs" | |||
There was a problem hiding this comment.
| contentType: "product-docs" | |
| contentType: "conceptual" |
| @@ -14,6 +14,7 @@ menu: | |||
| parent: "libraries" | |||
| weight: 004 | |||
| toc: true | |||
| contentType: "product-docs" | |||
There was a problem hiding this comment.
| contentType: "product-docs" | |
| contentType: "tutorial" |
| @@ -7,6 +7,7 @@ lastmod: 2024-05-02T08:49:15+00:00 | |||
| draft: false | |||
| images: [] | |||
| weight: 20 | |||
| contentType: "how-to-guide" | |||
There was a problem hiding this comment.
I feel like the index pages sit outside of the contentTypes
SharpRake
left a comment
There was a problem hiding this comment.
third review (hit submit too early). Approving! LMK if you have any questions
| @@ -9,6 +9,7 @@ images: [] | |||
| tags: ["Learning Labs", "Overview"] | |||
| toc: true | |||
| hidepageslist: true | |||
| contentType: "conceptual" | |||
There was a problem hiding this comment.
I think all the learning labs types could use more thought, most are more hands on than conceptual, no?
| @@ -0,0 +1,275 @@ | |||
| # Content Type Taxonomy Guide | |||
There was a problem hiding this comment.
I should have read this first, this is very helpful 🙃
| | **integration** | "How do I use X with Y?" | "Using Chainguard Images with GitHub Actions" | | ||
| | **conceptual** | "What is this?" | "What is an SBOM?" | | ||
|
|
||
| ## Examples by Directory |
There was a problem hiding this comment.
double check that these examples align with the final state after you make changes (if you make any at all)
…th-scanners/false-results.md Co-authored-by: Mark Drake <[email protected]> Signed-off-by: ltagliaferri <[email protected]>
Co-authored-by: Mark Drake <[email protected]> Signed-off-by: ltagliaferri <[email protected]>
Co-authored-by: Mark Drake <[email protected]> Signed-off-by: ltagliaferri <[email protected]>
Co-authored-by: Mark Drake <[email protected]> Signed-off-by: ltagliaferri <[email protected]>
| parent: "administration" | ||
| toc: true | ||
| weight: 008 | ||
| contentType: "tutorial" |
There was a problem hiding this comment.
| contentType: "tutorial" | |
| contentType: "product-docs" |
| parent: "chainctl-usage" | ||
| weight: 025 | ||
| toc: true | ||
| contentType: "conceptual" |
There was a problem hiding this comment.
| contentType: "conceptual" | |
| contentType: "product-docs" |
| parent: "administration" | ||
| toc: true | ||
| weight: 010 | ||
| contentType: "how-to-guide" |
There was a problem hiding this comment.
tutorial is more for introducing someone to something vs. how-to which is giving someone who know the general route a more detailed map
| parent: "pull-through-guides" | ||
| toc: true | ||
| weight: 005 | ||
| contentType: "product-docs" |
There was a problem hiding this comment.
I guess this is more of a question of whether you think it should sit with the product docs or not. I think I would lump integrations and product docs together for now
| contentType: "product-docs" | |
| contentType: "integration" |
| }, | ||
| ] | ||
|
|
||
| contentType: "conceptual" |
There was a problem hiding this comment.
I am thinking we should get rid of them but I need to check with some other stakeholders on that.
Co-authored-by: Mark Drake <[email protected]> Signed-off-by: ltagliaferri <[email protected]>
Co-authored-by: Mark Drake <[email protected]> Signed-off-by: ltagliaferri <[email protected]>
This introduces content types in the metadata so we can better organize content. It also has scripts for working with the content locally and READMEs for contributors.